-
-
Notifications
You must be signed in to change notification settings - Fork 43
feat(controller): support serverless serving with keda support by k8s scale subresource. #500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
fea7121 to
b73e6f0
Compare
|
/kind feature |
|
@pacoxu @googs1025 @carlory @kerthcet Hello all! Could you spare a few minutes to review my PRs when you have a chance? Other ref PRs: |
|
/assign |
|
@pacoxu @kenwoodjw Friendly ping, do you have some time to take a look at my PRs? Thanks a lot for your assistance! |
|
/assign |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems some docs are duplicated with https://github.com/InftyAI/llmaz/pull/499/files, can we just put one here and refer to it in another one.
@kerthcet Thank you for catching this! I've refactored the documentation structure to eliminate duplication, Now focuses specifically, and reference link to the main serverless documentation (PR #499) |
Signed-off-by: X1aoZEOuO <[email protected]>
Signed-off-by: X1aoZEOuO <[email protected]>
Signed-off-by: X1aoZEOuO <[email protected]>
Signed-off-by: X1aoZEOuO <[email protected]>
6ff79f5 to
9b47451
Compare
What this PR does / why we need it
Detailed Explanation of Commit
This commit introduces a guide for configuring serverless environments on Kubernetes, focusing on integrating Prometheus for monitoring and KEDA for autoscaling. The guide aims to optimize resource efficiency through event-driven scaling while maintaining observability for AI/ML workloads.
Which issue(s) this PR fixes
Fixes #
Special notes for your reviewer
Does this PR introduce a user-facing change?
cc @pacoxu @kerthcet